Defining privileges in association with the automated configuration, implementation and/or maintenance of a healthcare information system

ABSTRACT

Systems, methods and computer-readable media having computer-executable instructions embodied thereon, for automated configuration, implementation and/or maintenance of a healthcare information system are provided. The systems, methods and computer-readable media of embodiments described herein utilize a number of information sources prior to initiation of configuration, implementation and/or maintenance to tailor or flex the process in a manner that is facility- and/or personnel-specific, thus alleviating solicitation of unnecessary information. Such information sources may include, by way of example only, one or more of facility- and/or personnel-specific content, facility and personnel profiles, site profiles, help and knowledge assistance information, and pre-configured content options. The more information to which the system has access prior to initiation of the configuration, implementation and/or maintenance process, the more tailored the configuration, implementation and/or maintenance may be and, accordingly, the less time and effort will be required by a user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 60/805,169, filed Jun. 19, 2006, entitled “AutomatedDesign, Build and/or Maintenance of a Healthcare Information System” andis a divisional application of U.S. application Ser. No. 11/765,233filed Jun. 19, 2007, the entirety of both is hereby incorporated byreference. This application is related by subject matter to U.S. patentapplication Ser. No. 11/765,221 entitled “Defining Privileges inAssociation with the Automated Configuration, Implementation and/orMaintenance of a Healthcare Information System,” filed on Jun. 19, 2007and is hereby incorporated by reference in its entirety.

BACKGROUND

Healthcare information systems are traditionally very institutionallycustomized and require a tremendous amount of time and effort toimplement from ground level or convert from a different system. This isprimarily because such systems are manually built which is a tediousprocess at best, generally taking several months and multiple in-personconsultant visits to accomplish.

In particular, security and/or privileges are generally associated on anindividualized basis. That is, for each individual having some access tothe healthcare information system, security/privileges must be defined.Such process is rather time consuming when viewed in the context of thevast number of personnel that may have some access to the healthcareinformation system for varying reasons, e.g., data entry, auditing,order access, and the like.

BRIEF SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to computerized systems,methods, and computer-readable media having computer-executableinstructions embodied thereon, for configuring, implementing, and/ormaintaining a customized healthcare information system. In embodiments,such configuring, implementing, and/or maintaining may include automateddesign and build of a customized healthcare information system from theground level or may be an automated converting or updating process of auser's existing healthcare information system. The systems and methodsof embodiments of the present invention utilize a number of informationsources prior to configuration/implementation/maintenance to tailor orflex the process in a manner that is facility and/or personnel specific,thus alleviating solicitation of unnecessary information. Suchinformation sources may include, by way of example only, one or more offacility- and personnel-specific content, facility and personnelprofiles, help and knowledge assistance information, and pre-configuredcontent. The more information to which the system has access forinitiation and run of the configuration/implementation/maintenanceprocess, the more tailored the process may be and, accordingly, the lesstime and effort will be required.

In embodiments, systems and methods of the present invention facilitateconfiguration, implementation, and/or maintenance of a healthcareinformation system through a series of screen displays designed tosolicit pertinent information from a user wherein each subsequent screendisplay is selected based, at least in part, upon information extractedfrom one or more previously presented screen displays. In oneembodiment, presentation of such screen displays is Web-based.

Accordingly, in one embodiment, the present invention relates to one ormore computer-readable media having computer-executable instructionsembodied thereof that, when executed, aid in defining privileges and/orsecurity based on position upon configuring, implementing and/ormaintaining a customized healthcare information system. The methodincludes receiving input of a position associated with a facility, theposition having at least one configurable privilege associatedtherewith, presenting the configurable privilege (e.g., displaying theconfigurable privilege to a user defining the privileges associated withthe position), receiving a configuration definition for the configurableprivilege and storing the configuration definition in association withthe privilege.

In an additional embodiment, the present invention relates to a userinterface configured for defining privileges based on position inconfiguring, implementing and/or maintaining a customized healthcareinformation system. The user interface includes a selected positionsdisplay portion and an instructional display portion. The selectedpositions display portion is configured to display a list of positionsassociated with a facility, each position in the list having at leastone configurable privilege associated therewith. The instructionaldisplay portion is configured to display instructions regarding one ormore tasks to be completed in order to define the configurable privilegeassociated with at least one of the positions displayed in the list.

In a further embodiment, the present invention relates to a method fordefining privileges based on position upon configuring, implementingand/or maintaining a customized healthcare information system. Themethod includes receiving input of a position associated with afacility, the position having at least one configurable privilegeassociated therewith, receiving a configuration definition for theconfigurable privilege(s), and storing the configuration definition inassociation with the configurable privilege(s).

In an additional embodiment, the present invention relates to one ormore computer-readable media having computer-executable instructionsembodied thereon that, when executed, aid in defining privileges basedon position in configuring, implementing and/or maintaining a customizedhealthcare information system. The method includes receiving input of aposition associated with a facility, the position having at least oneconfigurable privilege associated therewith, receiving a configurationdefinition for the configurable privilege, determining if theconfiguration definition is consistent with at least one otherconfiguration definition associated with the position, and storing theconfiguration definition in association with the configurable privilege.

Still further, embodiments of the present invention relate to a userinterface configured for defining privileges based on position inconfiguring, implementing and/or maintaining a customized healthcareinformation system. The user interface includes a selected positionsdisplay portion, an instruction display portion and a reconciliationalert display portion. The selected positions display portion isconfigured to display a list of positions associated with a facility,each position in the list having at least one configurable privilegeassociated therewith. The instructional display portion is configured todisplay instructions regarding one or more tasks to be completed todefine the at least one configurable privilege associated with at leastone of the positions displayed in the list. The reconciliation alertdisplay portion is configured to display a reconciliation alert if it isdetermined that a configuration definition associated with a givenposition is inconsistent with at least one other configurationdefinition associated with the given position.

In a further embodiment, the present invention relates to a method fordefining privileges based on position in configuring, implementingand/or maintaining a customized healthcare information system. Themethod includes receiving input of a position associated with afacility, the position having at least one configurable privilegeassociated therewith, receiving a configuration definition for the atleast one configurable privilege, determining if the configurationdefinition is consistent with at least one other configurationdefinition associated with the position and storing the configurationdefinition in association with the at least one configurable privilege.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are described in detail below withreference to the attached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments of the present invention;

FIG. 2 is a block diagram of an exemplary system architecture for use inimplementing embodiments of the present invention;

FIG. 3 is a flow diagram, in accordance with an embodiment of thepresent invention, illustrating a method for configuring, implementingand/or maintaining a healthcare information system;

FIG. 4 is a screen display of an exemplary user interface that may bedisplayed upon user initiation of a process configured to permitselection of processes that commonly occur in an ambulatory setting thatthe user desires to automate, such processes typically occurring beforeor during a patient visit and/or configured to manage orders placed inthe office or clinic, in accordance with an embodiment of the presentinvention;

FIG. 5 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface that may be displayedupon selection of the “Preparing charts for patient appointments andtransferring patient information from paper to electronic format”hyperlink of FIG. 4;

FIG. 6 is a screen display of an exemplary user interface that may bedisplayed to permit user selection of processes that commonly occur inan ambulatory setting that the user desires to automate, such processestypically occurring outside of an office visit and/or including healthinformation management, billing, and administrative management, inaccordance with an embodiment of the present invention;

FIG. 7 is a screen display of an exemplary user interface that may bedisplayed to permit user selection of processes that commonly occur inan ambulatory setting that the user desires to automate, such processespertaining to documentation, in accordance with an embodiment of thepresent invention;

FIG. 8 is a screen display of an exemplary user interface configured topermit a user to associate positions that exist in a healthcareinformation system being utilized by the user that is other than thehealthcare information system being configured, implemented and/ormaintained with categories to be utilized for setting privilegesavailable to personnel assigned to that position, in accordance with anembodiment of the present invention;

FIG. 9 is a screen display, in accordance with an embodiment of thepresent invention, illustrating a list of positions for which securitymay be configured in association with an office or clinic a user desiresto automate;

FIG. 10 is a screen display of an exemplary user interface illustratinga list of those positions that were selected in the screen display ofFIG. 9, each position being selectable to initiate the defining ofsecurity pertinent thereto, in accordance with an embodiment of thepresent invention;

FIG. 11 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to scheduling, location,allergies, problems and diagnosis, and procedures;

FIG. 12 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to immunization, healthrecords, and orders and charges;

FIG. 13 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to prescriptions,medication profiles and clinical notes;

FIG. 14 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to structureddocumentation;

FIG. 15 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to forms, pediatric growthchart, patient history, and flow sheets;

FIG. 16 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to tasks and inbox;

FIG. 17 is a screen display, in accordance with an embodiment of thepresent invention, of an exemplary user interface configured to permit auser to define position security with respect to various activities;

FIG. 18 is a screen display, in accordance with an embodiment of thepresent invention, that may be displayed upon user selection of securitysettings that require further clarification;

FIG. 19 is a screen display, in accordance with an embodiment of thepresent invention, that may be displayed upon selection of the “Finish”selectable indicator of FIG. 18 illustrating a list of personnel thathave been assigned to the position for which security has been set thatprovides the user with the opportunity to update or not update eachmember of the list in accordance with the security settings;

FIG. 20 is a screen display illustrating an alert that may be displayedupon user selection or de-selection of a security setting that is atodds with another security setting, in accordance with an embodiment ofthe present invention;

FIG. 21 is a screen display illustrating an alert that may be displayedupon user selection or de-selection of a security setting that is atodds with another security setting, in accordance with an embodiment ofthe present invention;

FIG. 22 is a screen display, in accordance with an embodiment of thepresent invention, that may be displayed upon user selection of securityprivileges that reasonably may be out of synch with one anotherpermitting the user to change or verify such selections;

FIG. 23 is a partial screen display, in accordance with an embodiment ofthe present invention, of an exemplary user interface configured topermit a user to define position security with respect to allergies,wherein the option entitled “Enter/Update a patient's allergies (AllergyProfile)” has been selected;

FIG. 24 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the“Enter/Update a patient's allergies (Allergy Profile)” option of FIG. 23may have on the options available to an end-user of the healthcareinformation system being configured, implemented and/or maintained;

FIG. 25 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the“Enter/Update a patient's allergies (Allergy Profile)” option of FIG. 23may have on the options available to an end-user of the healthcareinformation system being configured, implemented and/or maintained;

FIG. 26 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the“Enter/Update a patient's allergies (Allergy Profile)” option of FIG. 23may have on the options available to an end-user of the healthcareinformation system being configured, implemented and/or maintained;

FIG. 27 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the“Enter/Update a patient's allergies (Allergy Profile)” option of FIG. 23may have on the options available to an end-user of the healthcareinformation system being configured, implemented and/or maintained;

FIG. 28 is a partial screen display, in accordance with an embodiment ofthe present invention, of an exemplary user interface configured topermit a user to define position security with respect to allergies,wherein the option entitled “No access to a patient's allergies (AllergyProfile)” has been selected;

FIG. 29 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the “No accessto a patient's allergies (Allergy Profile)” option of FIG. 28 may haveon the options available to an end-user of the healthcare informationsystem being configured, implemented and/or maintained; and

FIG. 30 is a screen display, in accordance with an embodiment of thepresent invention, illustrating the effect selection of the “No accessto a patient's allergies (Allergy Profile)” option of FIG. 28 may haveon the options available to an end-user of the healthcare informationsystem being configured, implemented and/or maintained.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention relate to computerized systems,methods and computer-readable media having computer-executableinstructions embodied thereon, for configuring, implementing, and/ormaintaining a customized healthcare information system. In embodiments,such configuring, implementing, and/or maintaining may include automateddesign and build of a customized healthcare information system from theground level or may be an automated converting or updating process of auser's existing healthcare information system. The systems and methodsof embodiments of the present invention utilize input from a number ofinformation sources prior to initiation ofconfiguration/implementation/maintenance to tailor or flex the processin a manner that is facility and/or personnel specific, thus alleviatingsolicitation of unnecessary information. Such information sources mayinclude, by way of example only, one or more of facility- andpersonnel-specific content, facility and personnel profiles, help andknowledge assistance information, and pre-configured content. The moreinformation to which the system has access for initiation and run of theconfiguration/implementation/maintenance process, the more tailored theprocess may be and, accordingly, the less time and effort will berequired.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 100. It will be understood andappreciated by those of ordinary skill in the art that the illustratedmedical information computing system environment 100 is merely anexample of one suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the medical information computing systemenvironment 100 be interpreted as having any dependency or requirementrelating to any single component/module or combination ofcomponents/modules illustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withembodiments of the present invention include, by way of example only,personal computers, server computers, hand-held or laptop devices,multiprocessor systems, microprocessor-based systems, set top boxes,programmable consumer electronics, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. The present invention may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inlocal and/or remote computer storage media including, by way of exampleonly, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 100 includes a general purpose computingdevice in the form of a server 110. Components of the server 110 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 112, with the server 110. The system bus maybe any of several types of bus structures, including a memory bus ormemory controller, a peripheral bus, and a local bus, using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The server 110 typically includes, or has access to, a variety ofcomputer-readable media, for instance, database cluster 112.Computer-readable media can be any available media that may be accessedby server 110, and includes volatile and nonvolatile media, as well asremovable and non-removable media. By way of example, and notlimitation, computer-readable media may include computer storage mediaand communication media. Computer storage media may include, withoutlimitation, volatile and nonvolatile media, as well as removable andnon-removable media implemented in any method or technology for storageof information, such as computer-readable instructions, data structures,program modules, or other data. In this regard, computer storage mediamay include, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVDs) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage, or other magnetic storage device, or any other medium which canbe used to store the desired information and which may be accessed bythe server 110. Communication media typically embodies computer-readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer-readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 112, provide storage of computer-readableinstructions, data structures, program modules, and other data for theserver 110.

The server 110 may operate in a computer network 114 using logicalconnections to one or more remote computers 116. Remote computers 116may be located at a variety of locations in a medical or researchenvironment, for example, but not limited to, clinical laboratories,hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. The remote computers 116 may also be physically located innon-traditional medical care environments so that the entire health carecommunity may be capable of integration on the network 114. The remotecomputers 116 may be personal computers, servers, routers, network PCs,peer devices, other common network nodes, or the like, and may includesome or all of the elements described above in relation to the server110. The devices can be personal digital assistants or other likedevices.

Exemplary computer networks 114 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the server 110 may include a modem or other means forestablishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the server 110, in the database cluster 112, or on any of the remotecomputers 116. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 116. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 110 and remote computers 116) may beutilized.

In operation, a user may enter commands and information into the server110 or convey the commands and information to the server 110 via one ormore of the remote computers 116 through input devices, such as akeyboard, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the server 110. In addition to a monitor, theserver 110 and/or remote computers 116 may include other peripheraloutput devices, such as speakers and a printer.

Although many other internal components of the server 110 and the remotecomputers 116 are not shown, those of ordinary skill in the art willappreciate that such components and their interconnection are wellknown. Accordingly, additional details concerning the internalconstruction of the server 110 and the remote computers 116 are notfurther disclosed herein.

Although methods and systems of embodiments of the present invention aredescribed as being implemented in a WINDOWS operating system, operatingin conjunction with an Internet-based system, one of ordinary skill inthe art will recognize that the described methods and systems can beimplemented in any system supporting the automated configuration,implementation and/or maintenance of a healthcare information system. Ascontemplated by the language above, the methods and systems ofembodiments of the present invention may also be implemented on astand-alone desktop, personal computer, or any other computing deviceused in a healthcare environment or any of a number of other locations.

As previously mentioned, the present invention relates to computerizedsystems and methods for the automated configuration, implementationand/or maintenance of a healthcare information system. Turning to FIG.2, an exemplary system architecture for use in implementing embodimentsof the present invention is illustrated and designated generally asreference numeral 200. It will be understood and appreciated by those ofordinary skill in the art that the overall system architecture 200 shownin FIG. 2 is merely an example of one suitable system architecture andis not intended to suggest any limitation as to the use or functionalityof the present invention. Neither should the overall system architecture200 be interpreted as having any dependency or requirement related toany single component/module or combination of components/modulesillustrated therein.

System 200 includes a survey component 210 configured to receive inputfrom a number of content components. Such content components include afacility- and personnel-specific content component 212, a facility andpersonnel profile content component 214, a knowledge portal 216 and apre-configured content component 218. It will be understood andappreciated by those of ordinary skill in the art that the number andnature of the inputs into the survey component 210 are merely exemplaryand are not intended to limit the scope of embodiments of the presentinvention in any way.

The facility- and personnel-specific content component 212 includeslocalized data derived from the particular facility, group offacilities, facility network, facility portion, or the like that desiresto configure, implement and/or maintain the customized healthcareinformation system. Such localized data may include, by way of exampleonly, clinician and other personnel lists, the physical address of oneor more healthcare locations operated by the user, the facilityorganization and design of one or more healthcare locations operated bythe user, patient profiles, user preferences, user-specific orderableitems and any associated aliases and/or collection requirements, workrouting preferences, and the like. Basically, the localized dataincludes any data that is unique to the particular facility, facilityportion, facility group, etc. that desires to configure, implementand/or maintain the healthcare information system in question and thatcannot be estimated or derived absent specific input or interaction withsuch data. Such data may be input into the facility- andpersonnel-specific content component 212 from a variety of sourcesincluding, by way of example only, data collected through Health Level 7(HL-7) mining 220 of the facility's existing healthcare informationsystem and/or data collected through facility- or personnel-specifictables or spreadsheets 222, which may be manually or automaticallypopulated. Facility- and personnel-specific content component 212 isgenerally utilized in situations where the facility (facility portion,facility group, or the like) has an existing healthcare informationsystem and desires to have such system updated or modified or to have adifferent healthcare information system configured and/or implemented.If necessary, upon extraction of data from the facility- andpersonnel-specific content component 212, such data is formatted to therequirements of the survey component 210 and input therein.

Facility and personnel profile component 214 includes high-level dataabout the nature of the facility (facility portion, facility group,etc.) and/or associated personnel. For instance, the facility andpersonnel profile component 214 may include data regarding whatparticular solutions the facility (facility portion, facility group,etc.) desires to have configured, implemented and/or maintained in itshealthcare information system or data regarding what type of healthcarefacility (facilities, facility portions, etc.) being operated (e.g., achildren's hospital, an academic hospital, or the like). Suchinformation is typically collected during cursory conversations ormeetings, or preliminary fact-finding scenarios with respect to aparticular facility (or the like) and input into the facility andpersonnel profile component 214. If necessary, upon extraction of datafrom the facility and personnel profile component 214, such data isformatted to the requirements of the survey component 210 and inputtherein.

Knowledge portal 216 is configured to access and/or provideinformational assistance data that will be available duringconfiguration, implementation and/or maintenance of the healthcareinformation system, such data generally being presented in a naturallanguage format. For instance, the knowledge portal 216 may include, byway of example only and not limitation, instruction on how to use thesurvey component 210, instruction on how to use a particular screendisplay presented during use of the survey component 210, informationregarding the reasoning for attempting to extract a particular piece ofdata from a user, data supporting the ramifications of selecting oneoption over another (including real-life examples), definitions ofterms, frequently asked questions, graphical displays, work charts,representations of front-end applications, and the like. Suchinformation may be input into the knowledge portal 216 from a variety ofsources including, by way of example only and not limitation, extractionfrom technical support documents 224. In this regard, data may notsimply be transferred from the technical support documents 224 into theknowledge portal 216 but may be converted from technical language to amore natural, user-friendly language upon input into the knowledgeportal 216.

The knowledge portal 216 may additionally include data input fromsurvey-learned data component 228, which component is more fullydiscussed herein below. If necessary, upon extraction of data from theknowledge portal 216, such data is formatted to the requirements of thesurvey component 210 and input therein.

Pre-configured content component 218 includes content that ispre-configured to be relevant in configuring, implementing and/ormaintaining the desired for building the healthcare information systemin question. In this regard, the pre-configured content may be based, atleast in part, upon the preferences and/or regulations of a particularhealthcare system, the preferences and/or regulations of healthcaresystems in a particular country or region, or the like. Thepre-configured content includes survey-specific tables that contain allof the options a user/facility may desire with respect to healthcareinformation system configuration, implementation and/or maintenance. Thepre-configured content further includes information regarding typicalhealthcare information system configurations for, e.g., particular typesof healthcare facilities, and the like. In this regard, if a facility(facility group, facility portion, or the like) does not have anexisting healthcare information system and, accordingly, such system isbeing configured and/or implemented from the ground level, suchconfiguration/implementation may be seeded with data derived from suchpre-configured, typical configurations as opposed to seeded withfacility- and personnel-specific data input from the facility- andpersonnel-specific content component 212 as would be the case if theuser had an existing healthcare information system. In one embodiment,content from each of the pre-configured content component 218 and thefacility- and personnel-specific content component 212 is input into thesurvey component 210 for utilization in configuring, implementing and/ormaintaining a healthcare information system. Any and all such variationsand combinations thereof are contemplated to be within the scope ofembodiments of the present invention.

Data concerning typical healthcare information system configurations andpreferences may be derived, at least in part, from survey-learnedinformation stored in association with survey-learned data component228. Survey-learned data component 228 includes data that has been minedor extracted from the survey-directed information store 226, whichinformation store contains data associated with each configuration,implementation and/or maintenance of the healthcare information system.Thus, with respect to the healthcare information system beingconfigured/implemented/maintained, the survey-directed information store226 includes clinical or common best practices, facilities data, and thelike. The survey-directed information store is more fully discussedherein below.

Survey component 210 is configured not only to receive various inputs asdescribed above, but also to present a plurality of screen displays fromwhich a user may input information to customize the healthcareinformation system being configured, implemented and/or maintained. Suchscreen displays may be presented on any type of computing device, forinstance, a user's personal computer, desktop computer, laptop computer,handheld device, consumer electronic device, and the like. It should benoted, however, that the invention is not limited to implementation onsuch computing devices, but may be implemented on any of a variety ofdifferent types of computing devices within the scope of embodiments ofthe present invention. Typically, presentation of the screen displayscomprises displaying the screen displays on a display device associatedwith a computing device as discussed above. However, other types ofpresentation, such as audible presentation, may also be provided withinthe scope of embodiments of the present invention.

The screen displays which are presented by the survey component 210 areselected based upon at least a portion of the information input into thesurvey component 210. Thus, the screen displays that are presented bythe survey component 210 are flexed based upon the information alreadyavailable to the survey component 210 prior to user interaction with thescreen displays. Accordingly, the screen displays that are available foruser input and interaction will vary for each facility (facility group,facility portion, etc.) configuring, implementing and/or maintaining thehealthcare information system in question. Additionally, as the userinteracts with each of the screen displays presented and inputsadditional information into the system, each subsequent screen displayis selected for presentation taking into account that information. Inthis way, the healthcare information system configuration,implementation and/or maintenance process is customized for eachfacility (facility group, facility portion, and the like), significantlydecreasing the time and effort suchconfiguration/implementation/maintenance may take. Customization of thehealthcare information system and exemplary user-directed screendisplays are discussed more fully herein below with reference to FIGS.4-30.

The survey component 210 is further configured to output facility- andpersonnel-specific data to a survey-directed information store 226 onceinformation has been input, and presented to and customized by a user.Only that information which was selected by and/or customized by theuser is output to the information store 226 and, as such, theinformation in the information store 226 is both facility- andpersonnel-specific and survey-directed. The information in thesurvey-directed information store 226 is subsequently available formining and extraction by the survey-learned data component 228 and, ifdesired, input into the pre-configured content component 218 and/orknowledge portal 216. In this way, the healthcare information system 200gets “smarter” with each configuration/implementation/maintenance run,that is, it has additional information available to it that allows it tofurther customize and direct the user through the process.

Turning to FIG. 3, a flow diagram is illustrated which shows anexemplary method 300 for automated configuration, implementation and/ormaintenance of a healthcare information system, in accordance with anembodiment of the present invention. Initially, as indicated at block310, an indication that a user associated with a facility (group offacilities, facility portion, or the like) desires to configure,implement or maintain a healthcare information system is received. Suchindication may be received, for instance, upon user selection of a“survey” icon present on the desktop of a display associated with theuser's computing device. Subsequently, an accessible facility and/orpersonnel profile for the facility (group of facilities, facilityportion, etc.) associated with the user is received, as indicated atblock 312. Such facility and/or personnel profile may be received, forinstance, by survey component 210 from facility and personnel profilecomponent 214 of FIG. 2.

Next, it is determined whether or not the facility(ies) associated withthe user has an existing healthcare information system. This isindicated at block 314. Such determination may be made, for instance, bysurvey component 210 of the system architecture 200 of FIG. 2. If it isdetermined that the facility(ies) associated with the user does have anexisting healthcare information system, facility- and/orpersonnel-specific content derived from the existing healthcareinformation system is subsequently received, as indicated at block 316.Such facility- and personnel-specific content may be received, forinstance, by survey component 210 from facility- and personnel-specificcontent component 212 of FIG. 2.

Subsequently, or if it is determined at block 314 that the facility(facilities, facility portion, or the like) associated with the userdoes not have an existing healthcare information system, pre-configuredcontent that is pre-configured to be relevant in configuring,implementing and/or maintaining the healthcare information system isreceived. This is indicated at block 318. Such pre-configured contentmay be received, for instance, by survey component 210 frompre-configured content component 210 of FIG. 2. Subsequently, prior to,or simultaneously, help and knowledge data is received, as indicated atblock 320. Such help and knowledge data may be received, by way ofexample only and not limitation, by survey component 210 of FIG. 2 fromknowledge portal 216.

It will be understood and appreciated by those of ordinary skill in theart that the order of steps 310, 312, 314, 316, 318, and 320 ispresented by way of example only and is not intended to limit the scopeof the invention in any way. Input from each of the various sources ofinformation may be received simultaneously, consecutively and/or in anyorder. Additionally, information from any one or more of the variousinformation sources may be received within embodiments hereof. All suchvariations are contemplated to be within the scope of embodiments of thepresent invention.

Once all available information has been received, the healthcareinformation system is configured, implemented, updated, and/ormaintained as indicated at block 322. Suchconfiguration/implementation/maintenance may be conducted, for instance,utilizing a series of screen displays presented to the user as describedhereinabove. (One exemplary series of screen displays for implementinggeneral lab order catalog functionality is more fully described belowwith reference to FIGS. 4-30.) Once the configuration, implementationand/or maintenance run is complete, the facility- andpersonnel-specific, survey-directed information is stored, as indicatedat block 324. Such information may be stored, for instance, in thefacility- and personnel-specific, survey-directed information store 226(or database) of the system architecture 200 of FIG. 2.

If desired, the survey-learned data may be mined, extracted, orotherwise retrieved for utilization in future implementations, updatesand/or maintenance of the healthcare information system. This isindicated at block 326. In one embodiment, the survey-learned data maybe extracted by survey-learned data component 228 from the facility- andpersonnel-specific, survey-directed information store 226 of FIG. 2utilizing data mining techniques known to those of ordinary skill in theart. Subsequently, as indicated at block 328, the survey-learned datamay be fed, for instance, in the pre-configured content component 218and/or the knowledge portal component 216 of FIG. 2. In this way, thesystem improves, or becomes “smarter,” with each consecutive run.

Turning now to FIGS. 4-7, a series of exemplary screen displays forselecting processes to be automated in association with a healthcareinformation system being configured, implemented and/or maintained isprovided. It will be understood and appreciated by those of ordinaryskill in the art that the series of screen displays presented in FIGS.4-7 is exemplary in nature and is not intended to limit the scope of theinvention in any way. Though not shown, it will additionally beunderstood and appreciated by those of ordinary skill in the art thatthe automated process selection process may be initiated upon userselection of an indicator representing such processes from a list ofavailable processes and/or processes that are to be completed prior tooperation of the healthcare information system being configured,implemented and/or maintained.

With initial reference to FIG. 4, an exemplary user interfaceillustrating a number of user-directed wizards that may be run in orderto configure and/or modify particular functionalities uponconfiguration, implementation and/or maintenance of a healthcareinformation system is illustrated and designated generally as referencenumeral 400. Note that each of the designated processes is provided witha natural language descriptor to help users more readily understand whathe is being asked to do. Such a more complete understanding may decreasethe time it takes a user to complete the automated process selectionmethod and, accordingly, increase user satisfaction.

User interface 400 includes a listing of available processes displayportion 402, each of the listed processes typically occurring before orduring a patient visit, a managed order display portion 404 including alist of available processes carried out to manage orders placed in theoffice or clinic, and a help and knowledge display portion 406. Theavailable processes display portion 402 is configured to displayselectable links for each process that typically occurs before or duringa patient visit that is available to the user during configuration,implementation and/or maintenance. Similarly, the managed order displayportion 404 is configured to display selectable links for each processthat is typically carried out to manage orders placed in the office orclinic that is available to the user during configuration,implementation and/or maintenance. The processes shown in the availableprocesses display portion 402 and the managed order display portion 404are selected based upon the information input into, for instance, thesurvey component 210 of the system architecture 200 of FIG. 2.Additionally, the user may complete a site profile (not shown) prior toinitiation of the healthcare information system configuration,implementation and/or maintenance and the information gleaned from suchsite profile may be input (e.g., into the facility and personnelprofiles component 214) prior to initiation of the automated processselection method. As the system has access to this information prior toinitiation of the healthcare information system functionalitiesdescribed herein, the processes shown are only those which pertain tothe user, relate to processes that are available in the healthcareinformation system the user is configuring, implementing and/ormaintaining, and that pertain to the phase of configuration,implementation and/or maintenance being run by the user. As such, eachof the display portions 402 and 404 of FIG. 4 will display customizedlists of processes for each user initiating configuration,implementation and/or maintenance of a healthcare information system.

The name or designation for each of the processes listed in theavailable processes display portion 402 and the managed order displayportion represents a selectable link to additional informationpertaining to the named process, such information being derived, forinstance, from the knowledge portal 216 of the system architecture 200of FIG. 2. By way of example only and not limitation, with reference toFIG. 5, an exemplary user interface that may be displayed upon selectionof the “Preparing charts for patient appointments and transferringpatient information from paper to electronic format” process listed inthe available processes display portion 402 of user interface 400 isillustrated and designated generally as reference numeral 500. Userinterface 500 includes an informational display portion 502 configuredto display information to the user that pertains to the selectedprocess, i.e., the chart preparation process. User interface 500additionally includes a help and knowledge display portion 502configured to display selectable links to data which may be helpful tothe user in determining if he would like to automate the selectedprocess. By way of example only, such data may include a process map,content to support the benefits and downsides of automating the selectedprocess, and/or recommendations. Such data may be derived, for instance,from the knowledge portal 216 of the system architecture 200 of FIG. 2.

Once the user has completed review of the information displayed in theinformational display portion 502, he may select the close indicator 504to close the display of user interface 500 and return to the userinterface 400 of FIG. 4.

Referring back to FIG. 4, the help and knowledge display portion 406 ofuser interface 400 is configured to display one or more selectable linksto additional information that may be of use to the user in completingthe healthcare information system configuration, implementation and/ormaintenance. Such additional information may be derived, for instance,from knowledge portal 216 of the system architecture 200 of FIG. 2.

User interface 400 additionally includes an instructional displayportion 408 and a selectable “Next” indicator 410. The instructionaldisplay portion 408 is configured to display instructions which informthe user what tasks he is to complete with respect to user interface400. As indicated in the instructional display portion 408, the user isto “[c]hoose from processes that commonly occur in an ambulatorysetting.” That is, the user is instructed to select the indicator boxnext to each of the processes designated in display portions 402 and 404that he desires to automate. Once the user has completed selection ofthe process(es) for which automation is desired, such processestypically occurring before or during a patient visit and/or typicallycarried out to manage orders placed in the office or clinic, he mayselect the selectable “Next” indicator 410. Selection of the “Next”indicator 410 may initiate display of the exemplary user interface 600of FIG. 6.

User interface 600 illustrates a number of additional processes that maybe automated upon configuration, implementation and/or maintenance of ahealthcare information system. User interface 600 includes an availableprocesses for patient care display portion 602 having a list ofavailable process for patient care that occur outside the office visit;an information management display portion 604 including a list ofmanagement-type processes, for instance, health information management,billing, and administrative management; and a help and knowledge displayportion 606. The available processes for patient care display portion602 is configured to display selectable links for each process forpatient care that typically occurs outside of the office visit that isavailable to the user for configuration, implementation and/ormaintenance. Similarly, information management display portion 604 isconfigured to display selectable links for each processes that istypically included in health information management, billing, andadministrative management that is available to the user forconfiguration, implementation and/or maintenance. The processes shown inprocesses for patient care display portion 602 and the informationmanagement display portion 604 are selected based upon the informationinput into, for instance, the survey component 210 of the systemarchitecture 200 of FIG. 2 and/or information gleaned from a siteprofile (e.g., input into the facility and personnel profiles component214). In this regard, the processes shown are only those which pertainto the user, relate to processes that are available in the healthcareinformation system the user is configuring, implementing and/ormaintaining, and that pertain to the phase of configuration,implementation and/or maintenance being run by the user. As such, eachof the display portions 602 and 604 of FIG. 6 will display customizedlists of processes for each user initiating configuration,implementation and/or maintenance of a healthcare information system.

The name or designation for each of the processes listed in processesfor patient care display portion 602 and the information managementdisplay portion 604 represents a selectable link to additionalinformation pertaining to the named process, such information beingderived, for instance, from knowledge portal 216 of the systemarchitecture 200 of FIG. 2.

The help and knowledge display portion 606 of user interface 600 isconfigured to display one or more selectable links to additionalinformation that may be of use to the user in completing the healthcareinformation system configuration, implementation and/or maintenance.Such additional information may be derived, for instance, from knowledgeportal 216 of the system architecture 200 of FIG. 2.

User interface 600 additionally includes an instructional displayportion 608, a selectable “Next” indicator 610, and a selectable“Finish” indicator 612. The instructional display portion 608 isconfigured to display instructions which inform the user what tasks heis to complete with respect to user interface 600. As indicated in theinstructional display portion 608, the user in the illustratedembodiment is to “[c]hoose from processes that occur outside the officeand other administrative processes.” That is, the user is instructed toselect the indicator box next to each of the processes designated indisplay portions 602 and 604 that he desires to automate.

Once the user has completed selection of the processes for whichautomation is desired from display portions 602 and 604, it isdetermined whether or not the user has selected any processes from userinterfaces 400 (FIG. 4) and 600 (FIG. 6) that require documentationoptions to be selected. Such processes requiring selection ofdocumentation options may include, by way of example only,“[d]ocumenting information obtained by the nursing staff while preparingthe patient to be seen by the provider”, “[p]rovider reviewing patientinformation, seeing the patient, and documenting the visit”,“[c]linician electronically placing patient prescriptions or addinghistorical medications into the patient's chart”, and “[c]linicianelectronically placing orders and charges”, each process being listed inthe available processes display portion 402 of FIG. 4.

If the user has selected one or more processes requiring selection ofdocumentation options, the selectable “Next” indicator 610 of the userinterface 600 of FIG. 6 will be available for selection by the user. If,however, the user has not selected one or more processes requiringselection of documentation options, the selectable “Next” indicator 610will not be available for selection by the user. In such case, the userwill typically select the selectable “Finish” indicator 612 to indicatecompletion of the selection of automated processes selection method.

If the “Next” indicator 610 is available for selection and selected bythe user, the exemplary user interface 700 of FIG. 7 may be displayed.User interface 700 includes a documentation options display portion 702and a help and knowledge display portion 704. The documentation optionsdisplay portion 702 is configured to display selectable links for eachdocumentation option that is available to the user for configuration,implementation and/or maintenance. The options shown in thedocumentation options display portion 702 are selected based upon theinformation input into, for instance, the survey component 210 of thesystem architecture 200 of FIG. 2 and the processes the user hasselected for automation that require selection of documentation options.In this regard, the options shown are only those which pertain to theuser, relate to options that are available in the healthcare informationsystem the user is configuring, implementing and/or maintaining, andthat pertain to the phase of configuration, implementation and/ormaintenance being run by the user. As such, the display portion 702 ofFIG. 7 will display a customized list of options for each userinitiating configuration, implementation and/or maintenance of ahealthcare information system.

The name or designation for each of the options listed in thedocumentation options display portion 702 represents a selectable linkto additional information pertaining to the named option, suchinformation being derived, for instance, from knowledge portal 216 ofthe system architecture 200 of FIG. 2.

The help and knowledge display portion 704 of user interface 700 isconfigured to display one or more selectable links to additionalinformation that may be of use to the user in configuring, implementingand/or maintaining the healthcare information system. Such additionalinformation may be derived, for instance, from knowledge portal 216 ofthe system architecture 200 of FIG. 2.

User interface 700 additionally includes an instructional displayportion 706 and a selectable “Finish” indicator 708. The instructionaldisplay portion 706 is configured to display instructions which informthe user what tasks he is to complete with respect to user interface700. As indicated in the instructional display portion 708 in theillustrated embodiment, the user has “noted in the previous pages thatnursing staff will be documenting information obtained while preparingthe patient to be seen by the provider and that the provider will bereviewing patient information, seeing the patient, placing orders andprescriptions, or documenting the visit.” Accordingly, the user is asked“[w]hich documentation options will the nursing staff and providers beusing to document patient information in the patient's chart?” That is,the user is instructed to select the indicator box next to one of theoptions designated in display portion 702 that describes thedocumentation option(s) the nursing staff and providers will be using.Once the user has completed selection of the desired documentationoption(s), he may select the selectable “Finish” indicator 708 toindicate completion of the automated processes selection method.

Turning now to FIGS. 8-22, a series of exemplary screen displaysrepresenting a process for defining security for each of the positionsin the clinical setting associated with a healthcare information systembeing configured, implemented and/or maintained is provided. It will beunderstood and appreciated by those of ordinary skill in the art thatthe series of screen displays presented in FIGS. 8-22 is exemplary innature and is not intended to limit the scope of the invention in anyway. Though not shown, it will additionally be understood andappreciated by those of ordinary skill in the art that thesecurity/privileges process may be initiated upon user selection of anindicator representing such process from a list of available processesand/or processes that are to be completed prior to operation of thehealthcare information system being configured, implemented and/ormaintained.

The process represented in FIGS. 8-22 permits user to assign privilegesat the position level such that all personnel designated to a particularposition will have the same security rights, absent any specificallydelineated exceptions. Assigning such privileges at the position levelalleviates the need for a user to designate security rights for eachindividual having access to the healthcare information system beingconfigured, implemented and/or maintained.

With initial reference to FIG. 8, an exemplary user interface configuredto permit a user to associate positions that exist in a healthcareinformation system being utilized by the user that is other than thehealthcare information system being configured, implemented and/ormaintained with categories to be utilized for setting privilegesavailable to personnel assigned to that position is shown and designatedgenerally as reference numeral 800. User interface 800 includes apositions with no association display portion 802, a work area orcategory designation display portion 804, and a positions withassociated areas display portion 806. The positions with no associationdisplay portion 802 is configured to display a list of those positionscurrently designated in the healthcare information system being utilizedby the user that is other than the healthcare information system beingconfigured, implemented and/or maintained. The displayed list ofpositions may be derived, for instance, from the facility and personnelprofiles component 214 of the system architecture 200 of FIG. 2. Thework area or category designation display portion 804 is configured todisplay a number of work areas or categories with which each of theunassociated positions may be associated. The positions with associatedareas display portion 806 is configured to display those positions whichhave been associated with a particular work area or category once suchdesignation is made by the user.

In practice, a user may select one of the positions listed in thepositions with no associated areas positions with no association displayportion 802 and subsequently select the check box next to one or morework area or category designations from the work area or categorydesignation display portion 804. The user may also indicate whetherpersonnel assigned to the position in question can place orders in theirown names in an order security display area 808. Once all work areas orcategories associated with the selected position have been designated,the user may select the “Save” indicator 810. Upon such selection, theposition in question will be moved from positions with no associationdisplay portion 802 to the positions with associated areas displayportion 806. The user may then repeat the process for each position thathas no category designation that he desires to categorize for purposesof setting security/privileges.

User interface 800 additionally includes an instructional displayportion 812 configured to display instructions which inform the userwhat tasks he is to complete with respect to user interface 800 anddetailed instructions regarding how to accomplish those tasks. Once allpositions displayed in the positions with no association display portion802 that the user desires to categorize have been categorized, the usermay select the selectable “OK” indicator 814 to begin settingsecurity/privileges for all positions he desires to automate.

Turning now to FIG. 9, an exemplary screen display illustrating a listof positions for which security may be configured in association with anoffice or clinic a user desires to automate is shown and designatedgenerally as reference numeral 900. User interface 900 includes apositions for selection display portion 902 and an instructional displayportion 904. The positions for selection display portion 902 isconfigured to display a list of positions for which security/privilegesmay be set for the healthcare information system being configured,implemented and/or maintained. The list of positions displayed may bederived, for instance, from pre-configured content component 218 and/orsurvey-learned data component 228 of system architecture 200 of FIG. 2.Additionally, if the user is updating the healthcare information systemsuch that there is already an available list of positions specific tothe user, for instance, from facility- and personnel-specific contentcomponent 212 of the system architecture 200 of FIG. 2, the list ofdisplayed positions may be flexed accordingly.

The instructional display portion 904 is configured to displayinstructions which inform the user what tasks he is to complete withrespect to user interface 900. In this regard, the instructional displayportion 904 contains instructions informing the user “[f]rom the listbelow, [to] select all the positions that work in the office or clinicyou are automating.” The user is also informed that the selections madewill determine future questions for these roles.

In practice, a user may select the check box displayed next to the nameor designation for each position listed in the positions for selectiondisplay portion 902 that he desires to automate. If a position isdesired that does not appear on the list, the user may select theselectable “Add” indicator 906 to free-text add a position or may selectthe selectable “Include Positions From Other Clinical Settings”indicator 908 to select additional positions from a different list ofpositions.

If the user hovers a pointer (e.g., a mouse pointer) over any of thepositions listed in the positions for selection display portion 902, atext box (not shown) configured to display a description of whatsecurity privileges personnel in that position typically have may bedisplayed. (Such information may be derived, for instance, frompre-configured content component 218 and/or survey-learned datacomponent 228 of system architecture 200 of FIG. 2.) In this way, if auser is unfamiliar with a particular position or acronym positiondesignation, he may easily obtain assistance in figuring out what thename or designation is intended to represent.

Once the user has selected each of the positions he desires to automatefrom the positions for selection display portion 902, he may select theselectable “Next” indicator 910. Upon such selection, the screen displayof FIG. 10 may be displayed. In FIG. 10, an exemplary user interfaceillustrating a list of those positions that were selected in the screendisplay of FIG. 9, each position being selectable to initiate thedefining of security pertinent thereto, is shown and designatedgenerally as reference numeral 1000. User interface 1000 includes aselected positions display portion 1002 and an instructional displayportion 1004 configured to display instructions which inform the userwhat tasks he is to complete with respect to user interface 1000. Inthis regard the instructional display portion 1004 informs the user thatthe positions he identified for the office or clinic being automated inFIG. 9 are shown and that he is to select one of the positions for whichestablishment of security settings is desired. Once the user hasselected one of the positions from the list of positions displayed inthe selected positions display portion 1002, he may select theselectable “Next” indicator 1006 to begin setting security/privilegesfor the selected position. In the illustrated example, the position of“Physician Assistant” has been selected.

It should be noted that user interface 1000 additionally includes a“Copy Security Settings” selectable indicator 1008. Selection ofindicator 1008 will permit the user to copy security settings that havealready been set with respect to one position to another position. Inthis way, significant time is saved in setting security settings forpositions for which there is commonality and/or for which similar oridentical privileges are desired.

Upon selection of the selectable “Next” indicator 1006 of user interface1000, a series of screen displays prompting selection of privileges forthe selected position are sequentially displayed. Initially, the screendisplay shown in FIG. 11 may be displayed. In FIG. 11, an exemplary userinterface configured to permit a user to define position security withrespect to viewing resource schedules, indicating arrival/location,allergies, problems and diagnosis, and procedures is shown anddesignated generally as reference numeral 1100. Once the user hasselected the desired privileges displayed on user interface 1100, he mayselect the selectable “Next” indicator 1102 to continue withsecurity/privileges designation.

Upon selection of the selectable “Next” indicator 1102 of FIG. 11, thescreen display shown in FIG. 12 may be displayed. In FIG. 12, anexemplary user interface configured to permit a user to define positionsecurity with respect to immunization records, health maintenancerecords, and orders and charges is shown and designated generally asreference numeral 1200. Once the user has selected the desiredprivileges displayed on user interface 1200, he may select theselectable “Next” indicator 1202 to continue with security/privilegesdesignation.

Upon selection of the selectable “Next” indicator 1202 of FIG. 12, thescreen display shown in FIG. 13 may be displayed. In FIG. 13, anexemplary user interface configured to permit a user to define positionsecurity with respect to prescriptions and medication profile andclinical notes is illustrated and designated generally as referencenumeral 1300. Once the user has selected the desired privilegesdisplayed on user interface 1300, he may select the selectable “Next”indicator 1302 to continue with security/privileges designation.

Upon selection of the selectable “Next” indicator 1302 of FIG. 13, thescreen display shown in FIG. 14 may be displayed. In FIG. 14, anexemplary user interface configured to permit a user to define positionsecurity with respect to structured documentation is illustrated anddesignated generally as reference numeral 1400. Once the user hasselected the desired privileges displayed on user interface 1400, he mayselect the selectable “Next” indicator 1402 to continue withsecurity/privileges designation.

Upon selection of the selectable “Next” indicator 1402 of FIG. 14, thescreen display shown in FIG. 15 may be displayed. In FIG. 15, anexemplary user interface configured to permit a user to define positionsecurity with respect to forms, pediatric growth chart, patient history,and viewing/commenting on patient results is illustrated and designatedgenerally as reference numeral 1500. Once the user has selected thedesired privileges displayed on user interface 1500, he may select theselectable “Next” indicator 1502 to continue with security/privilegesdesignation.

Upon selection of the selectable “Next” indicator 1502 of FIG. 15, thescreen display shown in FIG. 16 may be displayed. In FIG. 16, anexemplary user interface configured to permit a user to define positionsecurity with respect to tasks and inbox is illustrated and designatedgenerally as reference numeral 1600. Once the user has selected thedesired privileges displayed on user interface 1600, he may select theselectable “Next” indicator 1602 to continue with security/privilegesdesignation.

Upon selection of the selectable “Next” indicator 1602 of FIG. 16, thescreen display shown in FIG. 17 may be displayed. In FIG. 17, anexemplary user interface configured to permit a user to define positionsecurity with respect to various activities is illustrated anddesignated generally as reference numeral 1700. Once the user hasselected the desired privileges displayed on user interface 1700, he mayselect the selectable “Next” indicator 1702 to continue withsecurity/privileges designation. At this point, the user has completeddesignation of security/privileges but one or more of the selectedprivileges may require clarification. If this is the case, one or moreuser interfaces may be displayed upon selection of the selectable “Next”indicator 1702 of FIG. 17 that prompt the required clarification. Onesuch exemplary screen display is shown in FIG. 18. It should be notedthat if no privileges have been selected that require clarification,selection of the selectable “Next” indicator 1702 of FIG. 17 may insteadinitiate display of the screen display of FIG. 19. FIG. 19 is more fullydescribed herein below.

Note that if the user is updating the healthcare information system suchthat there is already available information pertaining to thesecurity/privileges available to personnel designated to certainpositions that is specific to the user, for instance, from facility- andpersonnel-specific content component 212 of the system architecture 200of FIG. 2, such selections may be defaulted for any of the screendisplays of FIGS. 11-17. Even if such information is defaulted, however,the user may still be provided with the option to change the previouslydesignated security/privileges for each position.

As previously stated, if clarification of security/privileges isrequired, one or more user interfaces may be displayed upon selection ofthe selectable “Next” indicator 1702 of FIG. 17 that prompt the requiredclarification. FIG. 18 shows one example of a clarification userinterface, such interface being designated generally as referencenumeral 1800. Note that the clarification prompts displayed on userinterface 1800 are customized and relevant to the illustrated selectionsmade in FIGS. 11-17. That is, any clarification user interfaces that aredisplayed will be flexed based on the previous security designations. Assuch, it will be understood and appreciated by those of ordinary skillin the art that user interface 1800 is merely exemplary. Once allclarification prompts displayed on user interface 1800 have beenaddressed, the user may select the selectable “Finish” indicator 1802 toindicate that setting of security/privileges is complete.

Upon selection of the selectable “Finish” indicator 1802 of FIG. 18, orif no clarification is required subsequent to user selection of theselectable “Next” indicator 1702 of FIG. 17, the screen display of FIG.19 may be displayed. In FIG. 19, an exemplary user interfaceillustrating a list of personnel that have been assigned to the positionfor which security has been set is shown and designated generally asreference numeral 1900. User interface 1900 provides the user with theopportunity to update or not update each member of the list inaccordance with the previously designated security settings. The usermay select each of the names on the displayed personnel list andindicate whether or not he would like the security settings to beupdated for that particular individual in accordance with the designatedsecurity settings. Once the user has indicated “yes” or “no” withrespect to each individual, the defining of security/privileges for thatposition is complete. The user may subsequently again initiate theprocess to define security/privileges for another position.Alternatively, a screen display (not shown) may be displayed promptingthe user to select another position for which to define security oraffirmatively state that he is finished with the security designationtask. Any and all such variations are contemplated to be within thescope of embodiments of the present invention.

Embodiments of the present invention provide the user with alerts orindicators if the user selects or de-selects a security/privilege optionthat creates an inconsistency with other tasks the personnel assigned tothat position designation may be set to be able to perform. Forinstance, with reference to FIG. 20, a screen display illustrating analert that may be displayed upon user selection or de-selection of asecurity/privilege setting that is at odds with anothersecurity/privilege setting is illustrated and designated generally asreference numeral 2000. In the illustrated embodiment, suppose the userhas previously indicated that personnel categorized as PhysicianAssistants are to have the ability to place orders in a physician'snotation portion of a patient's electronic medical record. Subsequently,and in accordance with this prior designation, upon displaying thescreen display wherein security with respect to orders and charges is tobe specified (e.g., screen display 1200 of FIG. 12), the selection whichindicates that that Physician Assistants are to be able to place ordersfor a patient and view the list of orders that have been placed for apatient may be selected as a default. If the user de-selects thisoption, the alert 2000 may be displayed informing the user thatde-selecting that particular task will also change the previouslydesignated security/privilege setting. The user may then be asked toaffirmatively state whether this is his intent before he is allowed toproceed. In this way, inconsistencies in the security/privileges beingset throughout the security process are flagged and reconciled prior tocompletion. Additionally, based on the user's selections during theconflict reconciliation process, indications of selection orde-selection of prior presented options may change. That is, if the userwere to scroll back through previously completed screen displays, one ormore options may appear changed from the selection(s) initially made bythe user, the changed selection(s) being in accordance with the user'sselections during the conflict reconciliation process.

FIG. 21 illustrates another example of the above-described conflictreconciliation functionality. In FIG. 21, a screen display illustratingan alert that may be displayed upon user selection or de-selection of asecurity setting that is at odds with another security setting is shownand designated generally as reference numeral 2100. In the illustratedembodiment, suppose the user has previously indicated that personnelcategorized as Physician Assistants are to have the ability to orderprescriptions in a physician's notation portion of a patient'selectronic medical record. Subsequently, and in accordance with thisprior designation, upon displaying the screen display wherein securitywith respect to prescriptions and the patient's medication profile is tobe specified (e.g., screen display 1300 of FIG. 13), the selection whichindicates that that Physician Assistants are to be able to prescribemedications, refill medications, and enter medications that the patienthas taken or is currently taking into their record may be selected as adefault. If the user de-selects this option, the alert 2100 may bedisplayed informing the user that de-selecting that particular task willalso change the previously designated security/privilege setting. Theuser may then be asked to affirmatively state whether this is his intentbefore he is allowed to proceed.

From the perspective of workflows in a clinical setting, there arecertain tasks that if an individual having a particular positiondesignation is permitted to participate in, it stands to reason thatthere are other tasks in which he should also be able to participate.Such corresponding “reasonable” tasks may be derived, for instance, frompre-configured content component 218 of the system architecture 200 ofFIG. 2, such content including survey-learned data. For instance, if anindividual having a particular position designation is permitted toupdate a patient's allergy profile, that same individual should also beable to view that patient's allergy profile. In such circumstances,embodiments of the present invention may provide an alert to the userasking for the user to either verify or synchronize any apparentinconsistencies. A screen display illustrating an alert that may bedisplayed upon user selection or de-selection of a security/privilegesetting that creates an apparent inconsistency is illustrated in FIG.22.

FIG. 22 shows a screen display that may be displayed upon user selectionof security privileges that reasonably may be out of synch with oneanother, such screen display being designated generally as referencenumeral 2200. In the illustrated embodiment, the user has indicated thatpersonnel assigned to the positions “BR Karen Test”, “Reg Clerk”, and“Tech, Cytology” are to have view and update privileges that areinconsistent with one another. Accordingly, the user is asked to eithersynchronize the privileges according to the previously set viewprivileges or update privileges, or to affirmatively indicate that heintends the privileges to remain out of synch. To synchronize theprivileges, the user may select each of the positions and indicate theprivileges he intends personnel assigned to the selected position tohave. When the user has completed the synchronization, he may select theselectable “OK” indicator 2202 to indicate that the task has beencompleted.

Each of the security/privilege selections made by a user utilizing thesecurity selection process according to embodiments of the presentinvention may have one or more effects concerning the options with whichpersonnel assigned to the pertinent clinical setting position may bepresented. By way of example, turning to FIGS. 23-30, a series ofexemplary screen displays are provided illustrating a plurality ofend-user effects selection or de-selection of a particularsecurity/privilege option in the security selection process describedherein above with reference to FIGS. 8-22 may have. It will beunderstood and appreciated by those of ordinary skill in the art thatthe screen displays presented in FIGS. 23-30 are exemplary in nature andare not intended to limit the scope of the invention in any way.

With initial reference to FIG. 23, a partial screen display of anexemplary user interface configured to permit a user to define positionsecurity with respect to allergies, wherein the option entitled“Enter/Update a patient's allergies (Allergy Profile)” has been selectedwith respect to personnel assigned to the category of PhysicianAssistant is illustrated and designated generally as reference numeral2300. When this option is selected, each of the screen displays shown inFIGS. 24-27 may be displayed to an individual assigned to the categoryof Physician Assistant when navigating through a patient's electronicmedical record. As can be seen, the option of “Allergy” is presented tothe end-user in screen display 2400 of FIG. 24 and the end-user ispresented with the option to view the allergy profile of the patient inthe screen display 2500 of FIG. 25. If the user elects in the screendisplay 2500 of FIG. 25 to view the patient's allergy profile, thescreen display 2600 of FIG. 26 illustrating the patient's allergyprofile may be displayed. In this instance, no allergies have beenrecorded in the patient's allergy profile. Upon selection of the“Allergies (0):” selectable link from the Summary display portion 2602of the screen display 2600 of FIG. 26, the screen display 2700 of FIG.27 may be displayed, wherein the end-user is permitted to select anoption to add a new drug allergy to the patient's allergy profile.

By way of contrast, the screen displays of FIGS. 28-30 illustrate thedifference in each of the above-described screen displays if the“Enter/Update a patient's allergies (Allergy Profile” security/privilegeoption of the screen display 2300 of FIG. 23 had not been selected. Inthis regard, in FIG. 28 a partial screen display of an exemplary userinterface configured to permit a user to define position security withrespect to allergies, wherein the option entitled “Enter/Update apatient's allergies (Allergy Profile)” has not been selected withrespect to personnel assigned to the category of Physician Assistant isillustrated and designated generally as reference numeral 2800. Whenthis option is not selected, each of the screen displays shown in FIGS.29 and 30 may be displayed to an individual assigned to the category ofPhysician Assistant when navigating through a patient's electronicmedical record. As can be seen with reference to the screen display 2900of FIG. 29, though the option of “Allergy” was presented to the end-userwhen the “Enter/Update a patient's allergies (Allergy Profile)” securityprivilege option was selected (FIG. 24), such is not only not availablebut not even displayed when the option is not selected. Similarly, withreference to the screen display 3000 of FIG. 30, when the “Enter/Updatea patient's allergies (Allergy Profile)” security/privilege option isnot selected, the end-user is not presented with the option to view theallergy profile of the patient. (Contrast this with the screen display2500 of FIG. 25 that may be displayed when the “Enter/Update a patient'sallergies (Allergy Profile)” security/privilege option is selected.) Asthe end-user is not allowed to view the patient's allergy profile, thescreen displays 2600 and 2700 of FIGS. 26 and 27, respectively, are notpresented to the end-user.

As can be understood, the present invention provides systems, methods,and computer-readable media having computer-executable instructionsembodied thereon for configuration, implementation and/or maintenance ofa healthcare information system. Such configuration, implementationand/or maintenance may include building of a healthcare informationsystem from the ground level or modifying or converting an existinghealthcare information system. Utilizing the systems, methods, andcomputer-readable media herein described, security/privilege conflictsare minimized as such inconsistencies are flagged and reconciliation isattempted prior to completion of the configuration, implementationand/or maintenance process. Additionally, as information is gleaned froma series of customized, pointed questions, and items for a user to electto select or de-select rather than from free-text information entry,elements that don't make sense from a clinical perspective are minimizedas well. For instance, entry of a diagnosis of penicillin (which doesn'tmake sense from a clinical perspective) would not be allowed.

The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Alternative embodiments will become apparent tothose of ordinary skill in the art to which the present inventionpertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and sub-combinationsare of utility and may be employed without reference to other featuresand sub-combinations. This is contemplated by and is within the scope ofthe claims.

1. A user interface configured for defining privileges based on positionin configuring, implementing and/or maintaining a customized healthcareinformation system, the user interface comprising: a selected positionsdisplay portion configured to display a list of positions associatedwith a facility, each position in the list having at least oneconfigurable privilege associated therewith; an instructional displayportion configured to display instructions regarding one or more tasksto be completed to define the at least one configurable privilegeassociated with at least one of the positions displayed in the list; anda reconciliation alert display portion configured to display areconciliation alert if it is determined that a configuration definitionassociated with a given position is inconsistent with at least one otherconfiguration definition associated with the given position.
 2. The userinterface of claim 1, wherein the reconciliation alert display portionis further configured to display a reasonable inconsistency alert if itis determined that the configuration definition associated with thegiven position is reasonably inconsistent with at least one otherconfiguration definition associated with the given position.
 3. The userinterface of claim 1, further comprising a description display areaconfigured to display a description of facility and/or industryprivileges generally associated with at least one of the positionsdisplayed in the list.
 4. The user interface of claim 1, furthercomprising a selectable copy indicator, selection of which initiatesassociation of privileges associated with a first position in the listof positions with a second position in the list of positions.